High availability for cloud servers

ABSTRACT

A high availability system in a cloud computing environment includes a snapshot manager disposed in a mirror environment having at least one computer server and a plurality of virtual machines disposed in a production environment. Each of the plurality of virtual machines includes a snapshot agent configured to perform a method. The method includes periodically taking snapshots of the virtual machine associated with the snapshot agent, determining a delta image based on a change between a current snapshot and a previous snapshot, removing previous snapshots in the virtual machine and transmitting the delta image to the snapshot manager. The snapshot manager is configured to store a recovery image for each of the plurality of virtual machines and to merge the received delta image with the recovery image to update the recovery image.

This application is a continuation application of the legally related U.S. Ser. No. 13/688,821 filed Nov. 29, 2012, the contents of which are incorporated by reference herein in their entirety.

BACKGROUND

The present invention relates to cloud servers, and more specifically, to high availability for cloud servers.

In general, cloud computing refers to server-based computing that allows users to transact with server resources using a variety of devices. Cloud computing applications are provided by a server, which allows users to use the applications without downloading and installing applications on their own device. Virtualization technologies commonly used in cloud computing enable the execution of multiple virtual machine instances with different operating systems on a single physical host. Each virtual machine instance functions independently as an isolated system with its own physical resources, OS and applications. Due to significant cost saving and efficiency, the virtualization model has been increasingly adopted by enterprises and service providers as their main computing and service delivery infrastructure, running critical internal business and external customer facing applications.

In order to minimize down time due to unexpected virtual machine crashes, a backup system is usually built into the infrastructure. Currently, there are many backup technology options available such as replication, mirroring and fail over clustering. Existing backup technologies are designed based on the traditional computing models and are costly to implement. In addition, these technologies can be complicated and tedious to maintain and often require additional expensive hardware and software components. With the widespread adaptation of cloud computing, due to its potential cost benefit and efficiency, the virtualization model has been increasingly adopted by enterprises and service providers.

SUMMARY

According to an exemplary embodiment, a high availability system in a cloud computing environment includes a snapshot manager disposed in a mirror environment having at least one computer server and a plurality of virtual machines disposed in a production environment. Each of the plurality of virtual machines includes a snapshot agent configured to perform a method. The method includes periodically taking snapshots of the virtual machine associated with the snapshot agent, determining a delta image based on a change between a current snapshot and a previous snapshot and transmitting the delta image to the snapshot manager. The snapshot manager is configured to store a recovery image for each of the plurality of virtual machines and to merge the received delta image with the recovery image to update the recovery image. In one embodiment, the snapshot manager is configured to identify and utilize an under utilized resource with the cloud computing environment for merging the received delta image with the recovery image to update the recovery image.

According to another exemplary embodiment, a computer program product for providing a high availability system in a cloud computing environment, the computer program product including a non-transitory storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method. The method includes creating a virtual machine in response to a user request and creating a snapshot agent for the virtual machine and registering the snapshot agent with a snapshot manager. The snapshot agent is configured to periodically take snapshots of the virtual machine associated with the snapshot agent, determine a delta image based on a change between a current snapshot and a previous snapshot and transmit the delta image to the snapshot manager. The snapshot agent is also configured to monitor a health of the virtual machine and to notify the snapshot manager if the virtual machine experiences abnormal behavior. The method also includes receiving a recovery image for the virtual machine from the snapshot manager in response to the virtual machine experiencing abnormal behavior and restoring the virtual machine with the recovery image.

According to yet another exemplary embodiment, a method for providing a high availability system in a cloud computing environment includes creating a virtual machine in response to a user request and creating a snapshot agent for the virtual machine and registering the snapshot agent with a snapshot manager. The snapshot agent is configured to periodically take snapshots of the virtual machine associated with the snapshot agent, determine a delta image based on a change between a current snapshot and a previous snapshot and transmit the delta image to the snapshot manager. The snapshot agent is also configured to monitor a health of the virtual machine and to notify the snapshot manager if the virtual machine experiences abnormal behavior. The method also includes receiving a recovery image for the virtual machine from the snapshot manager in response to the virtual machine experiencing abnormal behavior and restoring the virtual machine with the recovery image.

Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the invention with the advantages and the features, refer to the description and to the drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The forgoing and other features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

FIG. 1 illustrates a schematic of an example of a cloud computing node in accordance with exemplary embodiments.

FIG. 2 illustrates a cloud computing environment in accordance with exemplary embodiments.

FIG. 3 illustrates a set of functional abstraction layers provided by a cloud computing environment in accordance with exemplary embodiments.

FIG. 4 illustrates a high availability system in a cloud computing environment in accordance with exemplary embodiments.

FIG. 5 illustrates a snapshot manager in accordance with exemplary embodiments.

FIG. 6 is a flowchart illustrating a method for providing a high availability cloud server in accordance with an exemplary embodiment.

FIG. 7 illustrates a cloud computing environment in accordance with exemplary embodiments.

DETAILED DESCRIPTION

Referring now to FIG. 1, FIG. 1 illustrates a schematic of an example of a cloud computing node. Cloud computing node 10 is only one example of a suitable cloud computing node and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless, cloud computing node 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 1, computer system/server 12 in the cloud computing node 10 is shown in the form of a general-purpose computing device. The components of computer system/server 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including system memory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, FIG. 2 illustrates a cloud computing environment 50. As shown, cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 2 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 3, FIG. 3 illustrates a set of functional abstraction layers provided by cloud computing environment 50 (shown in FIG. 2). It should be understood in advance that the components, layers, and functions shown in FIG. 3 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes, in one example IBM® zSeries® systems; RISC (Reduced Instruction Set Computer) architecture based servers, in one example IBM® pSeries® systems; IBM® xSeries® systems; IBM® BladeCenter® systems; storage devices; networks and networking components. Examples of software components include network application server software, in one example IBM® WebSphere® application server software; and database software, in one example IBM® DB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter, WebSphere, and DB2 are trademarks of International Business Machines Corporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers; virtual storage; virtual networks, including virtual private networks; virtual operating systems; and virtual clients.

In one example, management layer 64 may provide the functions described below. Resource provisioning provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal provides access to the cloud computing environment for consumers and system administrators. Service level management provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment provides pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA. The management layer 64 also includes a forecasting-based service assignment module.

Workloads layer 66 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation; software development and lifecycle management; virtual classroom education delivery; data analytics processing; and transaction processing. Further, other types of workloads may also include web service workloads, enterprise applications such as billing and customer relationship management, various banking and finance applications, etc.

Referring now to FIG. 4, a high availability system 100 in a cloud computing environment in accordance with an exemplary embodiment is shown. As illustrated the high availability system 100 includes a production environment 110 and a mirror environment 120. In exemplary embodiments, the production environment 110 may be disposed on one or more servers and the mirror environment 120 is disposed on one or more remote servers, which may be located in a separate physical location. In exemplary embodiments, the one or more servers and one or more remote servers are configured to communicate with one another through a variety of known methods.

The production environment 110 includes a load balancer 112, a plurality of virtual machines 114 and a database 118. In exemplary embodiments, the load balancer 112 receives communications from users of the system 100 and directs the communications to an appropriate virtual machine 114. The load balancer 112 may also be configured to manage the virtual machines 114 in the production environment 110. For example, the load balancer 112 may be configured to create new instances of virtual machines 114 in response to user requests. Each of the plurality of virtual machines 114 includes one or more applications and a snapshot agent 116. In exemplary embodiments, the snapshot agents 116 are configured to communicate with a snapshot manager 122, which is located on the mirror environment 120. In exemplary embodiments, the database 118 is configured to store the snapshots generated by the snapshot agent 116 and may also store base, or start-up images, that are used to create new instances of virtual machines 114.

In exemplary embodiments, the snapshot agent 116 is configured to periodically take snapshots of the virtual machine 114. In exemplary embodiments, a snapshot includes both the state and the data of a virtual machine 114 at a specific point in time. The data includes all of the files that constitute the virtual machine which includes, but is not limited to, disks, memory, and other devices, such as virtual network interface cards. In exemplary embodiments, the snapshot agent 116 may be configured to take an initial snapshot of a virtual machine 114, or to load a known base image from database 118 that serves as a snapshot for a newly created virtual machine 114, the initial image is referred to as the base image or parent image. This base image can also be sent from the snapshot agent 116 or the database 118 to the snapshot manager 122.

In exemplary embodiments, the snapshot agent 116 is configured to periodically take snapshots of the virtual machine 114. The snapshot agent 116 waits a period of time that can be determined via configuration or other intelligent algorithms which can calculate the best snapshot taking interval to optimize performance of the virtual machine 114. In exemplary embodiments, the snapshot agent 116 is configured to generate a delta image, which includes the changes that occurred in a virtual machine 114 in between captured snapshots. After creating the delta image the snapshot agent 116 transmits the delta image to the snapshot manager 122 and the snapshot agent 116 updates its base or parent image. The snapshot manager 122 receives the delta image from the snapshot agent 116 and merges, via the snapshot merger 124, the delta image with the base image to create a recovery image for the virtual machine 114. The snapshot manger 120 is configured to store the recovery images for the virtual machine 114 in a memory device 116.

In exemplary embodiments, each virtual machine 114 includes a snapshot agent 116 that is configured to receive virtual machine 114 operating data and to collect snapshots a configurable time interval. The snapshot agent 116 is also configured to send the snapshots to the mirror environment 120 for processing by the snapshot manager 122. In exemplary embodiments, the snapshot agent 116 may be configured to receive an image to start or restart a virtual machine 114. The snapshot agent 116 may include a policy engine that controls the snapshot collection and merging operations. In exemplary embodiments, the policy engine may collect system and application performance information and decide how frequently a snapshot should be taken. In addition, the policy engine may also decide the frequency of merging so as to optimize the performance of the entire system as a whole. In exemplary embodiments, the snapshot agent 116 may be configured to continuously monitor the health of the virtual machine 114 and may notify the snapshot manager 122 if the virtual machine 114 experiences abnormal behavior or crashes to enable the snapshot manager 122 to take corrective backup actions.

Referring now to FIG. 5, a snapshot manager 122 in accordance with an exemplary embodiment is shown. In exemplary embodiments, snapshot manager 122 resides and runs on the mirror environment 120. In exemplary embodiments, the mirror environment 120 is a remote system which is configured to utilize resources that are not currently being utilized by the cloud. In addition, the location of the snap shot manager 120 can be migrated to another location within the cloud or outside of the cloud in response to workload fluctuation to minimize operation overhead. The snapshot manager 122 maintains a registry 132 for snapshot agents 116 and the registry 132 is responsible for updating the snapshot collection policy or configuration of the snapshot agents 116. The snapshot manager 122 communicates with each of the snapshot agents 116 and retrieves the most recent fully committed copy of any the virtual machines 114 running on in the production environment 110. The snapshot manager 122 receives delta images 102 collected by the snapshot agents 116 and performs merging, via the snapshot merger 124, with their respective parents as soon as the delta images 102 are received. The resulting recovery image 104 is then stored in the memory device 126 and is available for recovery purposes. In exemplary embodiments, a repository 128 may be used as a secondary storage component to provide backup storage for the recovery images for each of the virtual machines 114.

In exemplary embodiments, the snapshot manager 122 may maintain an array of standby virtual machines instances 130 in separate hosts with the recovery image as a direct replacement in case a virtual machines 114 experiences abnormal behavior or crashes, as observed by the snapshot agent 116. The collection of standby virtual machine instances 130 mirror the virtual machines 114 and are inactive until they are configured to replace their associated virtual machine 114.

Referring now to FIG. 6, a flowchart illustrating a method 200 for providing a high availability cloud server is shown. As shown at block 202, the method 200 includes creating a virtual machine instance in a production environment per a customer request. Next, as shown at block 204, the method 200 includes creating a snapshot agent for the virtual machine and registering the snapshot agent with a snapshot manager. In exemplary embodiments, upon registration of the snapshot agent, the snapshot manager will instantiate the snapshot agent with a specified policy engine (or default if no preference is set) together with an operation policy. As shown at block 206, the method 200 includes the snapshot agent acquiring a copy of the base image used by the virtual machine.

As shown at block 208, the method 200 includes the snapshot agent taking snapshots of the virtual machine. Next, as shown at block 210, the method 200 determining a delta image based on a change between a current snapshot and a previous snapshot and transmitting the delta image to the snapshot manager. In exemplary embodiments, delta images from multiple virtual machines can be sent to the mirror environment individually or as a batch. Next, as shown at block 212, the method includes removing previous snapshots in the virtual machine. As shown at block 214, the method also includes merging the received delta images with a recovery image stored by the snapshot manager to update the recovery image. As shown at block 216, when a virtual machine experiences a failure and a recovery is needed, the snapshot manager retrieves the recovery image from the snapshot manager and restores the virtual machine. In exemplary embodiments, the snapshot manager may create standby instance of the virtual machines according to service level requirements of the virtual machines. For example, not all virtual machines need standby instances, some virtual machines will tolerate a small delay in powering on the virtual machines from the mirror virtual machines images.

Referring now to FIG. 7, a timeline 300 illustrating the state of the snapshot images of an active virtual machine 302 and a mirror virtual machine 304 is shown. The size of both active and mirror virtual machine images grow with time with the mirror image always behind the active image with the running delta. Since the backup snapshots are copied to a remote host, merging can be done immediately upon new snapshot arrival while the merging of snapshots on the active virtual machine can be performed at longer interval. In exemplary embodiments, an algorithm or policy can be used to determine the most optimized time for snapshot collection and merging operation. In exemplary embodiments, with continuous snapshot collection the recovery image of the virtual machine is updated continuously. In exemplary embodiments, the high availability servers enable seamless and continuous virtual machine operation with negligible interruption.

In exemplary embodiments, the method for providing a high availability cloud server is configured to utilize unused resources in the cloud environment for the snapshot managers. In one embodiment, the snapshot manager may be configured to identify unused, or under utilized, resources in the cloud to automatically migrate to the identified resources. In another embodiment, the snapshot manager may rely on an external tool to identify unused, or under utilized, resources in the cloud to and may migrate to the identified resource.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, steps, operations, elements, and/or components, but do not preclude the presence or addition of one more other features, integers, steps, operations, element components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

The flow diagrams depicted herein are just one example. There may be many variations to this diagram or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order or steps may be added, deleted or modified. All of these variations are considered a part of the claimed invention.

While the preferred embodiment to the invention had been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described. 

What is claimed is:
 1. A method for providing a high availability system in a cloud computing environment, the method comprising: creating, by a processor, a virtual machine in response to a user request; creating a snapshot agent for the virtual machine and registering the snapshot agent with a snapshot manager, wherein the snapshot agent is configured to: periodically take snapshots of the virtual machine associated with the snapshot agent, wherein the snapshot includes all of the files that constitute the virtual machine including a state and a data of a virtual machine at a specific point in time; determine a delta image based on a change between a current snapshot and a previous snapshot; remove previous snapshots in the virtual machine; transmit the delta image to the snapshot manager; and monitor a health of the virtual machine and to notify the snapshot manager if the virtual machine experiences abnormal behavior; receiving a recovery image for the virtual machine from the snapshot manager in response to the virtual machine experiencing abnormal behavior; and restoring the virtual machine with the recovery image, wherein the snapshot manager is configured to store the recovery image for the virtual machine and to merge the received delta image with the recovery image to update the recovery image; wherein the snapshot agent comprises a policy engine configured to control snapshot collection, and wherein the policy engine is configured to collect system and application performance information for the virtual machine and to responsively determine how frequently snapshots are taken.
 2. The method of claim 1, wherein the snapshot manager is configured to store the recovery image for the virtual machine and to merge the received delta images with the recovery image to update the recovery image.
 3. The method of claim 1, wherein the snapshot manager is configured to create a standby instance of the virtual machine based on the recovery image.
 4. The method of claim 3, wherein the standby instance of the virtual machine is used to replace to virtual machine in the event of a crash of the virtual machine. 